Khalid and Rival on the JetBrains blog cover what .NET Aspire is, who it is for, and what JetBrains is doing to support this new approach to developing distributed applications on the .NET platform. Also, for all you internals geeks, we have a few details about the inner workings of our JetBrains Rider plugin.
Nick addresses some of the feedback of .NET Aspire. It's been 2 months since the release of the first preview, and Microsoft has been hard at work, so let's see where Aspire is going and if it has a bright future ahead of it.
In this video Saaed talks about how it .NET Aspire works and checking different parts of it.
If you want to utilize Entity Framework in a basic .NET Aspire application, adding a project to contain the entity models, context, and Entity Framework references and supporting a database engine container is a recommended place to get started. I suspect this guidance may be refined as .NET Aspire evolves.
.NET Aspire is a way to define your distributed system, and then IaC & Deployment tooling have to pick up the slack getting your definition out there, is this a good thing?